✓

I. Legal Framework & Thresholds

Core legal requirements and EU threshold values for 2024

▼

🎯 EU Threshold Values (2024)

€143,000
Central Government
€354,000
Sub-central authorities
€5,538,000
Works contracts
€750,000
Utilities sector
Source: Commission Delegated Regulation (EU) 2023/2495 of 15 November 2023

⚖️ Legal Framework

GWB (Gesetz gegen Wettbewerbsbeschränkungen): German Competition Act governing above-threshold procurement

VgV (Vergabeverordnung): Procurement Regulation implementing EU directives

UVgO (Unterschwellenvergabeordnung): Below-threshold procurement regulation

Legal Sources:
• GWB: Latest version from BGBl. I S. 674 (2021)
• VgV: BGBl. I S. 624 (2016), last amended 2021
• UVgO: Model regulation by Federal Ministry for Economic Affairs and Climate Action
⚠️ Service Provider Pitfall

Different rules apply above/below thresholds. Ensure you understand which legal framework governs your specific tender to avoid compliance issues.

🔄

II. Procurement Procedures (Vergabeverfahren)

Complete overview of all German procurement procedures and their applications

▼

🔓 Offenes Verfahren (Open Procedure)

Process: Single-stage procedure where any interested party can submit tenders

Timeline: Minimum 35 days for submissions (52 days if sent by post)

Best for: Standard IT services, software licenses, hardware procurement

Legal Basis: § 15 VgV, Art. 27 Directive 2014/24/EU
⚠️ Common Mistakes

Late submissions are automatically rejected - no exceptions. Ensure you submit well before the deadline and account for technical upload issues.

🔒 Nicht-offenes Verfahren (Restricted Procedure)

Process: Two-stage - Initial qualification phase, then invitation to tender

Timeline: 30 days qualification + 30 days tender submission

Best for: Complex IT projects, custom software development

Legal Basis: § 16 VgV, Art. 28 Directive 2014/24/EU
⚠️ Qualification Risk

Even qualified suppliers can be excluded in stage 2. Don't assume qualification guarantees contract award - maintain competitive pricing and technical excellence.

🤝 Verhandlungsverfahren (Negotiated Procedure)

Process: Direct negotiations with selected suppliers

Timeline: Flexible, depends on negotiation complexity

Conditions: Only permitted in specific circumstances (urgency, failed procedures, technical specificity)

Legal Basis: § 17 VgV, Art. 26, 32 Directive 2014/24/EU
⚠️ Limited Availability

Requires strict justification. Contracting authorities must prove no other procedure is suitable. Don't rely on this procedure being available.

🏆 Wettbewerblicher Dialog (Competitive Dialogue)

Process: Multi-stage dialogue to develop solutions

Timeline: Extended process with multiple dialogue rounds

Best for: Large-scale digital transformation, complex innovative solutions

Legal Basis: § 18 VgV, Art. 30 Directive 2014/24/EU
⚠️ Resource Intensive

Requires significant time and resource investment with no guarantee of success. Budget for multiple dialogue rounds and solution development costs.

🚀 Innovationspartnerschaft (Innovation Partnership)

Process: Structured partnership for research, development and subsequent purchase

Timeline: Divided into research/development phases with milestones

Maximum duration: Research phase typically 2-3 years

Best for: Cutting-edge technology development, innovative solutions not available on market

Legal Basis: § 19 VgV, Art. 31 Directive 2014/24/EU
⚠️ Development Risk

No guarantee the authority will purchase the developed solution. Intellectual property arrangements must be carefully negotiated upfront to protect your investment.

📦 Rahmenvereinbarungen (Framework Agreements)

Process: Umbrella contracts establishing terms for future call-offs

Duration: Maximum 4 years

Types: Single supplier or multiple supplier frameworks

Legal Basis: § 21 VgV, Art. 33 Directive 2014/24/EU
⚠️ Call-off Competition

Being on a framework doesn't guarantee work. Multi-supplier frameworks often require mini-competitions for each call-off, maintaining competitive pressure.

📄

III. EVB-IT Contract System

The five core standardized IT contract types for German public sector procurement

▼

📋 EVB-IT Contract Structure Overview

Each EVB-IT contract type consists of two legally binding components:

  • Main Contract (Hauptvertrag): Core contractual terms and specific requirements
  • General Terms & Conditions (AGB/GTCs): Standardized supplementary conditions
Official Source: Federal CIO Office (CIO Bund) - Current EVB-IT versions
⚠️ Two-Tier Legal System

Both the main contract AND the associated GTCs are legally binding. Service providers must comply with ALL provisions across both documents.

🖥️ EVB-IT System (Complete IT Systems)

Main Contract Covers:

  • Complete IT system creation and integration
  • System architecture and technical specifications
  • Integration of hardware, software, and services into functioning systems
  • System commissioning and acceptance testing

Associated AGB System Include:

  • System warranty periods (typically 24-36 months)
  • System-wide performance guarantees
  • Integration liability and system functionality obligations
  • System maintenance and lifecycle management

Typical Applications: Enterprise Resource Planning (ERP) systems, Content Management Systems (CMS), Human Resources suites, custom business applications, integrated IT infrastructure projects

Current Version: EVB-IT System v5.0 (2023) + AGB System v5.0
⚠️ System Integration Complexity

Complete system responsibility means the contractor is liable for the entire system functioning as a whole, not just individual components. Factor in comprehensive testing and integration costs.

⚙️ EVB-IT Erstellung (Software Development & Creation)

Main Contract Covers:

  • Development methodology and project phases
  • Functional and technical specifications
  • Testing, acceptance and delivery procedures
  • Documentation and training deliverables

Associated AGB Erstellung Include:

  • Intellectual property ownership rules
  • Change request and scope management
  • Defect liability periods (typically 24 months)
  • Source code delivery and technical documentation
Current Version: EVB-IT Erstellung v5.0 (2023) + AGB Erstellung v5.0
⚠️ IP Ownership Issues

Public sector often requires full IP transfer. This may conflict with your standard licensing models or reusable components strategy.

🔧 EVB-IT Dienstleistung (IT Services & Support)

Main Contract Covers:

  • Service scope and delivery specifications
  • Service level agreements (SLAs) and metrics
  • Staffing requirements and qualifications
  • Reporting and documentation obligations

Associated AGB Dienstleistung Include:

  • Performance penalties and service credits
  • Escalation procedures and governance
  • Staff security clearance requirements
  • Continuous improvement obligations
Current Version: EVB-IT Dienstleistung v5.0 (2023) + AGB Dienstleistung v5.0
⚠️ SLA Penalties

Service credit penalties can significantly impact revenue. Build buffer capacity and robust monitoring to ensure SLA compliance from day one.

🔄 EVB-IT Pflege (Maintenance & Support)

Main Contract Covers:

  • Maintenance scope and service specifications
  • Response times and resolution targets
  • Preventive maintenance schedules
  • Update and patch management procedures

Associated AGB Pflege Include:

  • Availability guarantees and uptime targets
  • Escalation procedures for critical issues
  • Long-term support obligations
  • Technology refresh and migration planning
Current Version: EVB-IT Pflege v5.0 (2023) + AGB Pflege v5.0
⚠️ Long-term Commitment Risks

Maintenance contracts often span multiple years with technology evolution risks. Plan for obsolescence and factor long-term support costs into pricing.

☁️ EVB-IT Cloud (Cloud Services & SaaS)

Main Contract Covers:

  • Service specifications and availability targets
  • Data location and sovereignty requirements
  • Scalability and performance metrics
  • Migration and onboarding procedures

Associated AGB Cloud Include:

  • Data protection and GDPR compliance
  • Security certification requirements (ISO 27001, etc.)
  • Disaster recovery and business continuity
  • Data portability and exit procedures
Current Version: EVB-IT Cloud v5.0 (2023) + AGB Cloud v5.0
⚠️ Data Sovereignty

German public sector often requires data to remain within EU/German borders. Ensure your cloud infrastructure can meet strict data residency requirements.

📋 Additional EVB-IT Contract Types

Beyond the five core contracts, additional specialized contract types are available for specific scenarios including Software Licensing, Data Center Services (AZ-Service), and specialized sector contracts. These follow the same two-tier structure with main contracts and corresponding AGBs.

Complete Contract Portfolio: View all current EVB-IT contracts and AGBs at CIO Bund

🔐 Cross-Cutting Compliance Requirements

GDPR & Data Protection:

  • Data Processing Agreements (DPA) mandatory under Art. 28 GDPR
  • Privacy by Design implementation required
  • Regular data protection impact assessments

Security Standards:

  • BSI IT-Grundschutz compliance often required
  • ISO 27001 certification frequently mandated
  • Regular penetration testing and security audits

Operational Requirements:

  • German-speaking support staff availability
  • Business continuity and disaster recovery plans
  • Regular reporting and governance meetings
Compliance References:
• GDPR: Regulation (EU) 2016/679
• BSI IT-Grundschutz: Current BSI Compendium
• ISO 27001: ISO/IEC 27001:2022 Information Security Management
⚠️ Certification Investment

Multiple certifications and ongoing compliance can cost €50k-200k annually. Include these operational costs in your long-term pricing strategy and contract negotiations.

📊

IV. Strategic Insights for Service Providers

Key success factors and common pitfalls to avoid in German public procurement

▼

💡 Winning Strategies

Early Market Engagement: Participate in market consultations and prior information notices to understand requirements before formal tenders

Reference Building: Develop relevant German public sector references through smaller initial contracts

Consortium Partnerships: Partner with established local firms for better market access and credibility

Compliance Excellence: Exceed minimum qualification requirements to differentiate from competitors

Market Intelligence Sources:
• TED Database: Official Journal of the EU for tenders
• BITKOM: German Digital Association procurement resources
• State procurement portals: Bayern, NRW, Baden-Württemberg

⚠️ Critical Pitfalls

Underestimating Bureaucracy: German procurement involves extensive documentation requirements and formal processes

Language Barriers: Contracts and communications often exclusively in German - ensure adequate language support

Cultural Differences: Long-term relationship building approach vs. transactional business models

Payment Terms: Public sector payment cycles typically longer than private sector (30-60+ days)

Cultural & Business References:
• GTAI: Germany Trade & Invest business guides
• German-American Chamber: Chamber of Commerce business resources
• DIHK: German Chamber of Commerce procurement guidance

📈 Market Intelligence & Opportunities

TED Database Monitoring: Track upcoming EU-wide tenders and market trends

State-level Platforms: Each Bundesland operates independent procurement portals with local opportunities

Framework Agreements: Multi-year revenue potential through strategic framework positioning

Industry Associations: Leverage BITKOM and eco Association for market insights and networking

Key Procurement Platforms by State:
• Bayern: vergabe24.bayern.de
• Nordrhein-Westfalen: vergabe.nrw.de
• Baden-Württemberg: service-bw.de
• Berlin: berlin.de/vergabeservice
• Federal Level: evergabe-online.de